Apparatus and method for managing application error

ABSTRACT

Methods and apparatus are provided for managing an application error. Error record information on at least one application in which an error has occurred is collected from at least one portable device. The collected error record information is stored in a table that maps error information of each application. An application list provision request is received from a portable device. At least one application to be filtered from an application list is identified based on the error information of each application mapped in the table. The application is filtered from the application list to generate a filtered application list. The filtered application list is provided to the portable device.

PRIORITY

This application claims priority under 35 U.S.C. §119(a) to KoreanApplication Serial No. 10-2013-0047549, which was filed in the KoreanIntellectual Property Office on Apr. 29, 2013, the entire content ofwhich is incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to an apparatus and a method formanaging an application error, and more particularly, to an apparatusand a method for managing an application error so as to exclude anapplication in which an error has occurred, when providing variousapplications.

2. Description of the Related Art

Applications are mounted in and are provided for service in a portabledevice, such as a mobile phone. Before being mounted in the portabledevice, it must be determined whether an application meets a qualityassurance standard of a telecommunication company. Additionally, inorder to produce applications such as a game, a messenger, utilities, orthe like, and to provide services of these applications in the portabledevice, execution and operation stability problems must be checked. Thevarious applications go through an individual quality assurance test forquality assurance.

The applications are tested and corrected many times by a developer, andthen are distributed by an operator or an application server. Theapplication server provides a list of various applications to theportable device of a user who is interested in purchasing anapplication. The list of the applications is displayed on the portabledevice, and the user may select and purchase a desired application.

In general, all applications that are operated based on a middlewareplatform, other than the middleware platform in a portable device, areincluded and serviced in the portable device with variousspecifications. Even when the applications have been tested andcorrected many times before being mounted in the portable device, anapplication error may not be entirely solved through a quality assurancetest, or the like.

The error may be in the application itself or may be generated by aquality problem of the middleware platform. It is difficult to identifya cause of a problem generated by the quality problem of the middlewareplatform, and an error occurrence frequency is high.

A problem may also be generated by an environmental distinctiveness in aprocess of supplying applications such as network environment, or thelike. In a current application quality verification system, it isdifficult to fundamentally solve the problem every time the problemoccurs. Accordingly, a developer should collect error information onwhat kind of error is generated in an application in order correct theoccurred error.

An operator of an application server or the like simply provides a listof various applications corresponding to specifications of the portabledevice to the portable device. However, the operator fails tosystemically manage the causes and types of the errors of the erroneousapplication.

SUMMARY OF THE INVENTION

The present invention has been made to address at least the aboveproblems and/or disadvantages and to provide at least the advantagesdescribed below. Accordingly, an aspect of the present inventionprovides an apparatus and a method for systemically managing anapplication in which an error has occurred.

Another aspect of the present invention provides an apparatus and amethod for managing an application error in order to prevent anapplication in which an error has occurred from being exposed to theportable device.

In accordance with another aspect of the present invention, a method isprovided for managing an application error in an application server.Error record information on at least one application in which an errorhas occurred is collected from at least one portable device. Thecollected error record information is stored in a table that maps errorinformation of each application. An application list provision requestis received from a portable device. At least one application to befiltered from an application list is identified based on the errorinformation of each application mapped in the table. The application isfiltered from the application list to generate a filtered applicationlist. The filtered application list is provided to the portable device.

In accordance with another aspect of the present invention, a method isprovided for managing an application error in a portable device. Errorrecord information is stored according to execution of at least oneapplication. The error record information on the at least oneapplication is transmitted to a server that manages error information ofeach application. An application list provision request is transmittedto the server. An application list that was filtered at the server basedon the error information of each application, is received in response tothe application list provision request.

In accordance with another aspect of the present invention, anapplication server is provided for managing an application error. Theapplication server includes an application error management unit thatcollects error record information on at least one application in whichan error has occurred from at least one portable device. The applicationserver also includes an error information database that stores thecollected error record information in a table that maps errorinformation of each application. The application server additionallyincludes an application filtering unit that identifies at least oneapplication to be filtered from an application list based on the errorinformation of each application mapped in the table when an applicationlist provision request has been received from a portable device, andthat filters the application from the application list to generate afiltered application list. The application server further includes anapplication provider that provides the filtered application list to theportable device.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of the presentinvention will be more apparent from the following detailed descriptionwhen taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a schematic diagram illustrating a construction of a systemfor managing an application error, according to an embodiment of thepresent invention;

FIG. 2 is a block diagram illustrating the inside of a portable deviceillustrated in the FIG. 1, according to an embodiment of the presentinvention;

FIG. 3 is a flowchart illustrating a process of transmitting andreceiving a message between a portable device and an application server,according to an embodiment of the present invention;

FIG. 4 is a flowchart illustrating a process of managing an applicationerror in an application server, according to an embodiment of thepresent invention; and

FIG. 5 illustrates an error information table, according to anembodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE PRESENT INVENTION

Embodiments of the present invention are described in detail more withreference to the accompanying drawings. The same or similar componentsmay be designated by similar reference numerals although they areillustrated in different drawings. Detailed descriptions ofconstructions or processes known in the art may be omitted to avoidobscuring the subject matter of the present invention.

While terms including ordinal numbers, such as “first” and “second,”etc., may be used to describe various components, such components arenot limited by the above terms. The terms are used merely to distinguishan element from the other elements. For example, a first element couldbe termed a second element, and similarly, a second element could bealso termed a first element without departing from the scope of thepresent invention. As used herein, the term “and/or” includes any andall combinations of one or more of the associated listed items.

The terms used in this application are for the purpose of describingparticular embodiments only and are not intended to be limiting of theinvention. As used herein, the singular forms are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. Terms such as “include” and/or “have” may be construed todenote a certain characteristic, number, step, operation, constituentelement, component or a combination thereof, but may not be construed toexclude the existence of or a possibility of the addition of one or moreother characteristics, numbers, steps, operations, constituent elements,components or combinations thereof.

Unless defined otherwise, all terms used herein have the same meaning ascommonly understood by those of skill in the art. Terms defined in agenerally used dictionary are to be interpreted to have meanings equalto the contextual meanings in the relevant field of art, and are not tobe interpreted to have ideal or excessively formal meanings unlessclearly defined in the present specification.

Embodiments of the present invention provide a method of systematicallymanaging an application error. Specifically, in embodiments of thepresent invention, information on an application in which an error hasoccurred is collected from a plurality of portable devices to make atable that maps error information of each application. Further, inembodiments of the present invention, when a portable device requestsprovisioning of a list of applications, a list of applicationscorresponding to the portable device with reference to the table isprovided to the portable device. Accordingly, it is possible to preventthe application in which an error has occurred from being exposed to theportable device, and to enable a stable display and distribution ofapplications.

FIG. 1 is a schematic diagram illustrating the construction of a systemfor managing an application error, according to an embodiment of thepresent invention. As shown in FIG. 1, a system for managing anapplication error includes one or more portable devices 100, 110, and120, an application server 130, a mobile communication service provider170, an application developer (development company) 180, and a manager190.

The portable device 100 loads and displays a list of applications whichcan be purchased and downloaded by accessing the application server 130,and performs operations such as purchase, login, search, and the like.The portable device 100 is equipped with a client that requests the listof applications from the application server 130 and purchases anddownloads a desired application.

When an error has occurred while an application is executed, theportable device 100 generates and stores information on an error recordfor the application, which includes, for example, a type of error, and acontent of error. The error record information represents a kind oferror that occurs in n application.

Since the type of application errors which usually occurs in theportable device 100 including the application is also changed accordingto the type of the portable device, there is a correlation betweeninformation of the portable device and the type of error. Therefore, theerror record information for the application may also includeinformation of the portable device. The error record information isperiodically or non-periodically transmitted to the application server130.

The portable device 100 may be embodied as a smart phone, a mobilephone, a game device, a Television (TV), a display device, avehicle-head unit, a laptop, a tablet Personal Computer (PC), a PersonalMedia Player (PMP), a Personal Digital Assistants (PDA), or the like.The portable device 100 may be implemented as a pocket-size portablemobile terminal having a portable terminal function, and a mobileterminal function, and a wireless communication function.

The application server 130 includes an application error management unit140, an error information DataBase (DB) 150, an application DB 155, anapplication filtering unit 160, and an application provider 165. Theapplication server 130 determines the applications, from among variousapplications, which the application server 130 will show to the portabledevices 100, 110, and 120 according to a predetermined policy. Inaddition, the application server 130 provides a list of applicationscorresponding to the predetermined policy to the portable devices 100,110, and 120, and provides a web environment required to purchase anddownload the applications.

The application error management unit 140 collects error recordinformation of each application transmitted from each portable device100, 110, and 120, and then stores the collected error recordinformation in the error information DB 150. The application errormanagement unit 140 periodically or non-periodically stores thecollected error record information in log form in the error informationDB 150. The application error management unit 140 statisticallyprocesses and arranges a type of error and a content of error for eachapplication, item by item. Specifically, the application errormanagement unit 140 may count the number of times an error has occurred,an error severity according to the number of times an error hasoccurred, or the like, for each application based on the statisticallyprocessed and arranged information.

Further, the application error management unit 140 consistently collectsthe error record information during a predetermined period, and maymanage the error information of each application based on an applicationin which an error has occurred and information of the portable device,item by item. The predetermined period may be determined according to arequest for an application developer, or the like.

The application error management unit 140 may not only store the errorinformation in the error information database (DB) 150 but also reportthe error information to the mobile communication service provider 170and the application developer (development company) 180. As a result,the application developer (development company) 180 can easily discoverand modify application errors, and the mobile communication serviceprovider 170 can provide a smooth application service.

The error information DB 150 stores a table that maps error informationaccording to each application. A predetermined error information tablein the error information DB 150 is implemented such that an applicationID, a name of an application, a number of times by which an error hasoccurred, relative importance, information of the portable device, orthe like, are arranged in a table form.

The application DB 155 stores applications developed through theapplication developer (development company) 180. FIG. 1 corresponds toan embodiment of the present invention in which the error information DB150 is implemented in the application server 130. However, the errorinformation DB 150 may exist outside of and be separated from theapplication server 130. Further, the application DB 155 may existoutside of the application server 130.

The application filtering unit 160 loads a list of basic applicationsfrom the application DB 155, according to a request to provide the listof applications from each of the portable devices 100, 110, and 120.Further, the application filtering unit 160 filters applicationscorresponding to the portable devices 100, 110, and 120 in the list ofbasic applications with reference to the error information DB 150.Specifically, the application filtering unit 160 determines a filteringcondition with reference to the error information DB 150 and selects anapplication to be filtered for each of the portable devices 100, 110,and 120 according to the filtering condition. The filtering conditionrefers to a condition for grading each application according to thenumber of times an error has occurred, an error severity, or the like,and then filtering-out an application having a grade higher than andequal to a predetermined threshold.

The application provider 165 provides the list of applications to theportable devices 100, 110, and 120 so as to enable display and purchaseof applications stored in the application DB 155. Specifically, theapplication provider 165 shows applications that can be downloaded andused from the portable device 100 connected to the application server130. More specifically, according to an embodiment of the presentinvention, the application provider 165 provides a list of applicationsfiltered for each of the portable devices 100, 110, and 120 to theportable devices 100, 110, and 120.

When the portable device 100 has made a request to provide anapplication list, a list of the applications filtered according to theportable device 100 is provided to the portable device 100 that has madethe request. The application provider 165 may configure and output aGraphical User Interface (GUI) so that each of the portable device 100,110, and 120 can request a list of applications and download a desiredapplication. The application provider 165 shows a list of applicationsexcept for applications in which many errors have occurred, using afiltering function through the GUI.

The manager 190 refers to an operator having highest access privilegesthat can control a filtering condition by accessing the applicationserver 130. The manager 190 having the highest access privileges is auser having a privilege that can cancel restrictions made by theapplication developer (development company) 180, and can access theapplication server 130 through a separately implemented manager site.The manager 190 may directly add a filtering condition, by itself, inaddition to the filtering condition made based on the error informationon applications provided by the portable devices 100, 110, and 120. Forexample, applications that should only be distributed to users over 18years of age in a specific nation may be unconditionally filtered, orapplications that belong to a specific category, e.g., a game, or thelike may be filtered.

Hereinafter, operations of the portable device, among elements of asystem managing an application error in which functions described aboveare implemented, is described with reference to FIG. 2. Sinceconstructions and operations of the portable devices 100, 110, and 120for managing an application error, according to an embodiment of thepresent invention, are similar to each other, elements of only oneportable device 100 and operations thereof will be described as anexample, with reference to FIG. 2.

FIG. 2 is a block diagram illustrating the inside of a portable deviceillustrated in the FIG. 1, according to an embodiment of the presentinvention. Referring to FIG. 2, the portable device 100 includes anapplication layer 200, a middleware platform 205, and a hardware layer210.

The application layer 200 executes application 1 215 and application 2220 on the middleware platform 205.

The middleware platform 205 provides an application program interfacethat can execute an application program. Various applications aredeveloped according to a function Application Program Interface (API)standard, which is defined by the middleware platform 205 of theportable device 100 so that services of the various applications can beprovided in the portable device 100. These applications may generate anerror by the applications themselves or due to problems such as theplatform, or the like. When an application error has occurred, an errorrecord analysis unit 255 analyzes the error record for the application.Errors may occur in various forms due to the service environment, aninternal problem, or the like. Therefore, according to an embodiment ofthe present invention, the error record analysis unit 255 configures anerror record having a type (e.g., code) of one of various errors from anetwork, a storage unit, GUI, a platform, or the like, so that theapplication server 130 can identify the kind of error and theapplication in which the error has occurred.

The hardware layer 210 is a layer in which physical hardware exists andincludes an error record DB 230 for storing the error record generatedby the error record analysis unit 255, and an error record reportingunit 235 for reporting the error record to the application server 130.

The error record DB 230 arranges and stores error record informationgenerated by the error record analysis unit 225, item by item. The errorrecord DB 230 is implemented in a storage unit of the portable device100. For example, a type (code) of an error, a content of an error, orthe like, in an application, is stored. A name of an application inwhich an error has occurred, a location of error occurrence, time oferror occurrence, and information on the portable device 100 in which anapplication error has occurred, may also be stored together.

The error record reporting unit 235 may transmit the error recordinformation stored in the error record DB 120 according to apredetermined period, or may non-periodically transmit the error recordinformation according to a request from the application server 130. Forexample, the error record reporting unit 235 transmits the error recordinformation according to a designated transmission period policy bychecking a period designated by the application server 130, e.g.,transmission every 6 hours, transmission every 24 hours, or the like.Further, the error record information may be transmitted when there is arequest from the application server 130.

FIG. 3 is a flowchart illustrating a process of transmitting andreceiving a message between a portable device and an application server,according to an embodiment of the present invention. Operations betweenthe portable device 100 and the application server 130 are describedwith reference to FIG. 3.

Referring to FIG. 3, when an error has occurred while an applicationthat has been downloaded is operated, the portable device 100 transmitsan error record for the application, in steps 300 to 310. Whenever anapplication error has occurred, the error record may be transmitted tothe application server 130. When there is a plurality of applications inwhich an error has occurred, the portable device 100 may store an errorrecord for the plurality of applications in a log form, and thentransmit the error record in log form according to the predeterminedperiod or non-periodically. Further, although the embodiment of thepresent invention illustrated in FIG. 3 corresponds to a case in whichan error record is transmitted before a request for a list ofapplications is transmitted, the error record may be transmittedaccording to the predetermined period or non-periodically. Therefore,the time point for transmission of the error record can be changed.

When the application error record has been received, the applicationserver 130 statistically processes application errors using the errorrecord and then stores the application error. In order to output thelist of applications on a screen, the application device 100 transmits arequest for a list of applications to the application server 130, instep 315. The request for the list of applications includes informationon the portable device 100 transmitting the request.

In response, the application server 130 provides a list of filteredapplications to the portable device 100, which requested the list ofapplications, in step 320. The list of the filtered applicationscorresponds to a list obtained by filtering-out applications in which anerror has occurred and applications corresponding to information on theportable device 100, e.g., a model of the portable device 100 from alist of basic applications. The application server 130 may excludeeither all applications in which an error has occurred or onlyapplications in which an error has occurred more than a predeterminednumber of times, according to an embodiment of the present invention.The application server 130 identifies an application to be excluded withreference to a table mapping the application error information.

FIG. 4 is a flowchart illustrating a process of managing an applicationerror in an application server, according to an embodiment of thepresent invention. Specific operations of the application server 130 forproviding the list of the filtered applications is described withreference to FIG. 4.

Referring to FIG. 4, the application server 130 collects an error recordfor an application from one or more portable devices 100, 110, and 120,in step 400. In step 405, the application server 130 generates the errorinformation DB 150 defining an application error level and the contentof an error based on the error record. Specifically, the applicationserver 130 stores the collected error record in a table that classifiesand stores error severity levels according to the number of times errorshave occurred in each application.

FIG. 5 illustrates a table stored in the error information DB 150,according to an embodiment of the present invention. Referring to FIG.5, the application server 130 stores error record information in theform of a table that maps error information of each application based onthe collected error record information. Specifically, error recordinformation collected from the portable devices 100, 110, and 120includes at least one of a name of an application in which an erroroccurs, a location of error occurrence, a time of error occurrence, andinformation on the portable device 100 in which an error has occurred inaddition to a type (code) of error, and a content of error in anapplication.

The table of FIG. 5 arranges application IDs 500, application names 505,the number of times an error has occurred 510, an error severity 515levels defined according to the number of times the error has occurred,item by item. Referring to FIG. 5, the application server 130 counts thenumber of times errors have occurred in each application and determineserror severity levels according to the number of times the error hasoccurred. For example, an error severity C (e.g., ‘MINOR’) may be givento a case in which the number of times the error has occurred is withina first threshold number of times, an error severity B (e.g. ‘CRITICAL’)may be given to a case in which the number of times the error hasoccurred exceeds the first threshold number of times and is within asecond threshold number of times, and an error severity A (e.g.,‘FATAL’) may be given to a case in which the number of times the errorhas occurred exceeds the second threshold number of times.

When the error severity level is ‘CRITICAL’ 520 and 530 or ‘FATAL’ 525,the application server 130 excludes an application having that errorseverity level from a list of basic applications to be provided to theportable device 100. Therefore, in the portable device 100, anapplication with a high error severity level is not exposed and a morestable application can be provided to a user.

While an embodiment of the present invention has been described in whichan application is filtered according to an error severity level, a tableadditionally including information of a portable device, e.g., a modellevel of the portable device, which enables an application to befiltered according to the information of the portable device, may beimplemented. For example, when a model level of the portable devicebelongs to a highest level, a list of all applications may be exposed.When the model level of the portable device belongs to a lowest level, alist of applications, excluding applications that are not supported bythe performance of the portable device, may be exposed.

Accordingly, the application server 130 may determine that anapplication is to be filtered from the list of basic applications basedon the error severity and information on the portable device, and mayexclude that application.

Further, although an embodiment of the present invention has beendescribed in which an error severity is determined according to thenumber of times by which an error has occurred, it is also possible toimplement a configuration in which the error severity is set based onthe type of error in the application. For example, it may be assumedthat the error severity level A corresponds to a case in which a graveproblem for use occurs, such as a case in which an application isforcibly terminated or the power of a device is forced off while theapplication is executed, the error severity level B corresponds to acase in which a problem for use occurs, for example, some of theapplications main functions do not normally operate, and the errorseverity level C corresponds to a case in which auxiliary functions ofan application do not normally operate. Accordingly, for the errorseverity level A, even when the number of times by which an error hasoccurred is small, the error may be fatal to the portable device.Therefore, the application server 130 may determine error severity byassigning a weighted value to the number of times by which an error hasoccurred according to the type of error.

Referring again to FIG. 4, after the error information DB is generatedas described above, the application server 130 determines whether afiltering condition is received from the manager 190, in step 410. Thefiltering condition received from the manager 190 is input through aseparate UI. For example, the filtering condition may includeapplication use age limits, a specific application limit in a specificnation, or the like. Therefore, since it is possible to adjust thefiltering condition through a manager site, the application filteringcondition can be set to meet requirements as needed.

When the filtering condition has been received, the application server130 updates the error information DB 150 after excluding an applicationsatisfying the filtering condition, in step 415. In contrast, when thefiltering condition is not received, the application server 130 proceedsto step 420. In step 420, the application server 130 determines whethera request for a list of applications is received from the portabledevice 100. Information of the portable device 100 is loaded in therequest for the application list.

When the request for the list of applications has been received, theapplication server 130 detects information of the portable device 100according to the request for the list of applications and provides thelist of the filtered applications in the list of basic applications tothe portable device 100 with reference to the error information DB 150and the information of the portable device 100, in step 425.Specifically, the application server 130 identifies an application thatshould not be exposed, based on error information of each application inthe error information DB 150 and the information of the portable device100.

According to embodiments of the present invention, a user collects errorrecords of several applications provided from various portable devicesso that an application in which an error has occurred can besystematically managed. Further, an application distribution company ora developing company can automatically filter-out an application inwhich an error has occurred, so as to have a positive effect on thestability of the application server and a supply of the application.

Further, according to embodiments of the present invention, the portabledevice can automatically transmit the error record information of anapplication in which an error has occurred to the application server.Therefore, embodiments of the present invention enable an applicationserver to prevent an application in which an error has occurred, frombeing exposed to the portable device, so as to enable a more stabledisplay and distribution of applications.

It may be appreciated that the embodiments of the present invention canbe implemented in software, hardware, or a combination thereof. Any suchsoftware may be stored, for example, in a volatile or non-volatilestorage device such as a Read Only Memory (ROM), a memory such as aRandom Access Memory (RAM), a memory chip, a memory device, or a memoryIntegrated Circuit (IC), or a recordable optical or magnetic medium suchas a Compact Disc (CD), a Digital Versatile Disc (DVD), a magnetic disk,or a magnetic tape, regardless of its ability to be erased or itsability to be re-recorded. It can be also appreciated that the memoryincluded in the mobile terminal is one example of machine-readabledevice suitable for storing a program including instructions that areexecuted by a processor device to thereby implement embodiments of thepresent invention. Therefore, embodiments of the present inventionprovide a program including codes for implementing a system or methodclaimed in any claim of the accompanying claims and a machine-readabledevice for storing such a program. Moreover, such a program as describedabove can be electronically transferred through an arbitrary medium suchas a communication signal transferred through cable or wirelessconnection, and embodiments of the present invention include equivalentsubject matter.

The portable device can receive the program from a program providingapparatus connected to the device, wirelessly or through a wire, andstore the received program. The program providing apparatus may includea memory for storing a program, a communication unit for performingwired or wireless communication, and a controller.

While the invention has been shown and described with reference tocertain embodiments thereof, it will be understood by those skilled inthe art that various changes in form and detail may be made thereinwithout departing from the spirit and scope of the invention as definedby the appended claims.

What is claimed is:
 1. A method of managing an application error in anapplication server, the method comprising the steps of: collecting errorrecord information on at least one application in which an error hasoccurred from at least one portable device; storing the collected errorrecord information in a table that maps error information of eachapplication; receiving an application list provision request from aportable device; identifying at least one application to be filteredfrom an application list based on the error information of eachapplication mapped in the table; filtering the application from theapplication list to generate a filtered application list; and providingthe filtered application list to the portable device.
 2. The method ofclaim 1, wherein the error record information comprises at least one ofa type of the error, a content of the error, a name of an application inwhich the error has occurred, a location of an error occurrence, a timeof the error occurrence, and information on a portable device in whichthe error has occurred.
 3. The method of claim 1, wherein storing thecollected error record information comprises classifying and storing anerror severity level according to a number of times an error hasoccurred.
 4. The method of claim 3, wherein filtering the applicationcomprises excluding the application that has an error security levelhigher than or equal to a predetermined level.
 5. The method of claim 1,further comprising: detecting model information of the portable devicefrom the application list provision request; and identifying theapplication to be filtered according to the model information of theportable device.
 6. The method of claim 1, further comprising: receivinga filtering condition from a manager of the application sever; andidentifying the application to be filtered according to the receivedfiltering condition.
 7. The method of claim 1, wherein the tablecomprises application IDs, names of each application, a number of timesan error has occurred, and an error severity according to the number oftimes the error has occurred, arranged item by item.
 8. A method ofmanaging an application error in a portable device, the methodcomprising the steps of: storing error record information according toexecution of at least one application; transmitting the error recordinformation on the at least one application to a server that manageserror information of each application; transmitting an application listprovision request to the server; and receiving a application list thatwas filtered at the server based on the error information of eachapplication, in response to the application list provision request. 9.The method of claim 8, wherein the error record information comprises atleast one of a type of an error, a content of the error, a name of anapplication in which the error has occurred, a location of an erroroccurrence, a time of the error occurrence, and information on theportable device in which the error has occurred.
 10. The method of claim8, wherein the application list provision request comprises informationon the portable device, which is referenced when the application list isfiltered.
 11. The method of claim 8, wherein the application list isobtained by excluding one or more applications having an error securitylevel higher than or equal to a predetermined level from the applicationlist, the error security level being classified according to a number oftimes an error has occurred in each application.
 12. An applicationserver for managing an application error, the application servercomprising: an application error management unit that collects errorrecord information on at least one application in which an error hasoccurred from at least one portable device; an error informationdatabase that stores the collected error record information in a tablethat maps error information of each application; an applicationfiltering unit that identifies at least one application to be filteredfrom an application list based on the error information of eachapplication mapped in the table when an application list provisionrequest has been received from a portable device, and that filters theapplication from the application list to generate a filtered applicationlist; and an application provider that provides the filtered applicationlist to the portable device.
 13. The application server of claim 12,wherein the error record information comprises at least one of a type ofthe error, a content of the error, a name of an application in which theerror has occurred, a location of an error occurrence, a time of theerror occurrence, and information on the portable device in which theerror has occurred.
 14. The application server of claim 12, wherein theapplication error management unit classifies error severity levelsaccording to a number of times an error has occurred in each applicationbased on the collected error record information, and stores theclassified error severity levels in the error information database. 15.The application server of claim 14, wherein the application filteringunit excludes the application that has an error security level higherthan or equal to a predetermined level, from the basic application list.16. The application server of claim 14, wherein the applicationfiltering unit detects model information of the portable device from theapplication list provision request, and identifies the application to befiltered according to the model information of the portable device. 17.The application server of claim 12, wherein the table comprisesapplication IDs, names of each application, a number of times an errorhas occurred, and an error severity according to the number of times theerror has occurred, arranged item by item.